-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix client no retry on good token #171
Fix client no retry on good token #171
Conversation
cviecco
commented
Jun 17, 2022
- The okta 2fa cope did not return an error message when no valid autneticators where available
- When both mfa AND token failed the client did not termiate on error conditins
@@ -362,6 +362,7 @@ func setupCerts( | |||
|
|||
} | |||
} | |||
logger.Debugf(1, "SetupCerts: authenticaiton Complete") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/authenticaiton/authentication/
} | ||
if len(userResponse.Embedded.Factor) < 1 { | ||
logger.Printf("oktaPushStartHandler: user %s does not have valid authenticators", authData.Username) | ||
logger.Debugf(2, "oktaPushStartHandler: usedata for broken user%s is :%s", authData.Username, userResponse) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/usedata/userdata/ ?
if err != nil { | ||
return PushResponseRejected, err | ||
} | ||
if userResponse == nil { | ||
return PushResponseRejected, nil | ||
} | ||
pa.logger.Debugf(2, "oktaAuthenticator: validsteUserPush: after getting userResponse=%+v", userResponse) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
validste
?
Is this PR still needed? Review comments are still open. |
Closed with new revision reopened |
Changes in PR #240. |